chore: rename recurring order FeatureId - #10631

Note

Medium Risk
Breaking public enum and string identifier change; clients still using recurring_buy will fail type-checks or send mismatched analytics until updated.

Overview
Breaking rename of the bridge FeatureId used for recurring flows: the enum member becomes RECURRING_ORDER with wire value 'recurring_order' instead of RECURRING_BUY / 'recurring_buy'.

The @metamask/bridge-controller Unreleased changelog documents the breaking change. Consumers must switch enum references and any hard-coded feature_id strings (e.g. when calling fetchQuotes or emitting unified swap/bridge analytics) to the new name so attribution stays aligned with Segment conventions.

^{Reviewed by Cursor Bugbot for commit cfdd67e. Bugbot is set up for automated code reviews on this repo. Configure here.}